Reader control system

ABSTRACT

An RFID reader control system and method is provided. A protocol for controlling an RFID reader and an RFID reader control unit of a mobile phone is defined. Messages, information, commands, responses, and notification are constructed and transmitted between the RFID reader and the RFID reader control unit.

TECHNICAL FIELD

The present invention relates to a reader control system.

BACKGROUND ART

The ISO and EPC standards define a reader protocol that supportsconnection of an RFID reader to a host through a network. In RFIDsystems, an RFID reader is mounted on a mobile phone or attached to amobile phone in a dongle configuration. Such RFID systems require aprotocol that enables an RFID reader control unit of the mobile phone tocontrol the RFID reader.

In mobile phone environments, an RFID system is employed between aprocessor (e.g., MPU and MCU) of a mobile phone and an RFID reader chipinstalled in the mobile phone. Alternatively, a reader protocol isemployed between a mobile phone and an RFID reader attached onto themobile phone in a dongle configuration. When an RFID reader is attachedonto a mobile phone in a dongle configuration, the RFID reader and themobile phone are connected by an interface unit such as UART or USB. Inthis case, an efficient protocol is needed between the RFID reader andthe mobile phone.

The ISO and EPC standards provide protocols that are applied mainly forthe case where an RFID reader is connected through a network. Thereforerequired is an RFID system including an RFID reader control protocolsuitable for mobile phone environments.

DISCLOSURE OF INVENTION Technical Problem

Accordingly, the present invention is directed to a reader controlsystem that substantially obviates one or more problems due tolimitations and disadvantages of the related art.

An object of the present invention is to provide a reader control systemand method suitable for mobile terminal environments. In the system andmethod, a protocol for controlling a reader and a reader control unit ofa mobile terminal is defined and messages, information, commands,responses, and notification are constructed and transmitted between thereader and the reader control unit.

Technical Solution

To achieve these objects and other advantages and in accordance with thepurpose of the invention, as embodied and broadly described herein,there are provided commands and responses that are exchanged between areader and a reader control unit such as a processor of a terminal.

In another aspect of the present invention, there are provided a readercontrol protocol format and respective fields that are used between areader and a reader control unit such as a processor of a terminal.

In another aspect of the present invention, there are provided protocolmessages, fields of each protocol message, and the content of eachfield, with respect to commands, responses, and notifications that areused in a reader control protocol that is performed between a reader anda reader control unit such as a processor of a terminal.

In a further aspect of the present invention, there is provided a methodof using respective fields of a reader control protocol format that isexchanged between a reader and a reader control unit such as a processorof a terminal.

In a further aspect of the present invention, there is provided a methodof constructing a message and information in a reader control protocolthat is performed between a reader and a reader control unit such as aprocessor of a terminal.

In a further aspect of the present invention, there is provided a methodof transmitting a message and/or information in a reader controlprotocol that is performed between a reader and a reader control unitsuch as a processor of a terminal.

In a further aspect of the present invention, there is provided a methodof constructing and transmitting a protocol bit stream in a readercontrol protocol that is performed between a processor, a reader, and areader control unit such as a processor of a terminal.

In a further aspect of the present invention, there is provided a methodof constructing and storing a message and/or information in a readercontrol protocol that is performed between a processor, a reader, and areader control unit such as a processor of a terminal.

In a further aspect of the present invention, there is provided a methodof controlling and managing a reader in a reader control protocol thatis performed between a processor, a reader, and a reader control unitsuch as a processor of a terminal.

In a further aspect of the present invention, there is provided a methodof reading, writing, changing, querying, protecting, and killing (ordeleting) a reader message and/or information in a reader controlprotocol that is performed between a processor, a reader, and a readercontrol unit such as a processor of a terminal.

In a further aspect of the present invention, there are provided aresponse and an error process to a message and/or information and theimplementation and use method of additional functions, in a readercontrol protocol that is performed between a processor, a reader, and areader control unit such as a processor of a terminal.

It is to be understood that both the foregoing general description andthe following detailed description of the present invention areexemplary and explanatory and are intended to provide furtherexplanation of the invention as claimed.

Advantageous Effects

According to the present invention, the present invention is directed areader control system and method suitable for mobile terminalenvironments. In the system and method, a protocol for controlling areader and a reader control unit of a mobile terminal is defined andmessages, information, commands, responses, and notification areconstructed and transmitted between the reader and the reader controlunit.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this application, illustrate embodiment(s) of the invention andtogether with the description serve to explain the principle of theinvention. In the drawings:

FIGS. 1 and 2 illustrate the configuration of mobile RFID systems towhich the present invention is applied;

FIG. 3 illustrates a mobile RFID reader control protocol formataccording to an embodiment of the present invention;

FIG. 4 through 6 illustrates a payload type according to an embodimentof the present invention; and

FIGS. 7 through 83 illustrate mobile RFID reader control protocolmessage structures according to embodiments of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

In the following embodiments of the present invention, a mobile terminal(e.g., a mobile phone) with an RFID reader control unit is taken as anexample of a terminal with an RFID reader control unit.

FIG. 1 illustrates a mobile RFID system configuration when a mobile RFIDreader is installed in a mobile phone. FIG. 2 illustrates a mobile RFIDsystem configuration when a mobile RFID reader is attached to theoutside of a mobile phone in a dongle configuration.

Referring to FIG. 1, a mobile phone 100 includes a mobile phoneprocessor 110 and a chip-type or module-type mobile RFID reader 120. Thepresent invention proposes a mobile RFID reader control protocolexecuted between the processor 110 and the RFID reader 120.

Referring to FIG. 2, a mobile phone 100 includes a mobile phoneprocessor 110 and a receptacle connector 120. A mobile RFID readerdongle 200 includes a chip-type or module-type mobile RFID reader 210and a receptacle connector 220. The RFID reader 210 is connected to themobile phone 100 by the receptacle connectors 120 and 220. The presentinvention proposes a mobile RFID reader control protocol executedbetween the processor 110 and the RFID reader 210.

Terms in the embodiments of the present invention are based on the MRFdocument ‘Term Definition of Mobile RFID Service Standards’. Forexample, the term ‘Q’ is a parameter used in a tag based on the ISO18000-6C standards. When a reader transmits the parameter Q to a tag,the tag generates (2^(Q)-1) time slots and sends a response insynchronization with one of the (2^(Q−1)) time slots.

[1] Format of Mobile RFID Reader Control Protocol

A mobile RFID reader control protocol according to an embodiment of thepresent invention includes a preamble, a header, a payload, and an endmark. FIG. 3 illustrates a format of a mobile RFID reader controlprotocol according to an embodiment of the present invention. A preambleincludes information for indicating the start of a protocol message,which is used to discern protocol messages. For example, the preamblemay be configured in 8 bits and may have a value of OxBB. A headerincludes information for indicating a message type, a correspondingcode, and a payload length. That is, payload length information isstored in the header. Information received from an RFID tag is stored inthe payload. An end mark includes information for indicating the end ofa protocol message, which is used to discern protocol messages togetherwith the preamble. For example, the end mark may be configured in 8 bitsand may have a value of Ox7E.

[1.1] Preamble Field and End Mark Field

For example, in each protocol message, the preamble and the end markeach have a 8-bit data, which indicate the start and end of the protocolmessage. The preamble and the end mark are located at the start and endof the protocol message, respectively, and have a predetermined value.For example, the preamble may have a value of OxBB, and the end mark mayhave a value of Ox7E. It is preferable that the preamble and the endmark have a different value than those used in a message type field anda code field of the header.

[1.2] Header Field

The header includes three fields describing an RFID tag type,command/response/notification type and code, and a payload length. Themessage type field is used to discern a command that is transmitted fromthe processor to the reader and a response and a notification that aretransmitted from the reader to the processor. The code field is used todiscern a variety of types of command, response or notification. Also,the code field includes information about success or failure of commandin response and notification. The payload length field includesinformation indicating the length of a payload located right after theheader, which represents the length in byte.

[1.2.1] Message Type Field

The message type field includes information about which one of acommand, a response and a notification in a protocol format, which maybe represented in a total of 8 bits. The message type (e.g., command,response and notification) can be discerned using values shown in Table1 below.

TABLE 1 Command/Response/ Corresponding Code Value Notification Type(Hexadecimal) Command 0x00 Response 0x01 Notification 0x02 Test Mode0x03 Reserved 0x04-0xFF

As shown in Table 1, a code value indicating a command is 0x00, a codevalue indicating a response is 0x01, a code value indicating anotification is 0x02, a code value indicating a test mode is 0x03, andcode values indicating “Reserved” are 0x04˜0xFF. The command, theresponse, the notification, and the test mode shown in Table 1 will bedescribed in detail later.

[1.2.2] Code Field

A code field is used to discern the types of a command, a response, anda notification. There may be various commands to be processed by amobile RFID reader. Also, there may be various responses to the commandsand various notifications to be sent by the reader. Therefore, when adifferent code is assigned to each kind of command, response andnotification, the reader can accurately discern them by referring to themessage type field and the code field. For example, when a value 0x00and a value 0x01 are respectively assigned to a message type field and acode field for a power control command, the reader can recognize areceived command as the power control command by the assigned values.

[1.2.3] Payload Length Field

A payload length field indicates the length of a payload field locatedafter a header field. For example, the payload length field may becomposed of 16 bits. Here, the unit of length is byte. When a payloadlength is represented in byte using 16 bits, the maximum representablelength becomes 65,536 bytes. This means that the maximum length of apayload cannot exceed 65,535.

[1.3] Payload Field

A payload field stores various types of data. The payload field mayinclude arguments related to a command transmitted from the processor tothe RFID reader, and various data contained in a response transmittedfrom the RFID reader to the processor. There may be various types ofpayloads suitable for respective commands and responses, such aspayloads illustrated in FIGS. 4 through 6. FIGS. 4 through 6 illustrateType A through Type X.

Each of the payloads illustrated in FIGS. 3 through 6 includes aspecific field. The use of the specific field and the method thereofwill be described in detail later. The generation and configuration ofeach payload type will now be described in detail. The number of bitsand order mentioned in the following payload configurations are merelyexamples, and the present invention is not limited to this.

A payload Type A includes an 8-bit argument.

A payload Type B includes a variable-length argument.

A payload Type C is generated to include an 8-bit modulation index, an8-bit byte mask, and an 8-bit address, which are transmitted in theorder named.

A payload Type D includes a 3-bit target, a 3-bit action, a 2-bit MB, a32-bit pointer, an 8-bit mask length, T, RFU (Reserved for Future Use),and a mask of maximum 25 bits, which are transmitted in the order named.

A payload Type E includes a 2-bit DR, a 4-bit M, a 2-bit TR, a 2-bitSel, a 2-bit S, T, a 4-bit Q, and a 3-bit UpDn, which are transmitted inthe order named.

A payload Type F includes a 16-bit argument 1 and an 8-bit argument 2,which are transmitted in the order named.

A payload Type G includes a 32-bit argument.

A payload Type H includes a 16-bit argument 1 and a variable-lengthargument 2, which are transmitted in the order named.

A payload Type I includes a 64-bit argument 1, a 16-bit argument 2, anda 16-bit argument 3, which are transmitted in the order named.

A payload Type J includes a variable-length argument 1, a 16-bitargument 2, and a 16-bit argument 3, which are transmitted in the ordernamed.

A payload Type K includes a 16-bit argument.

A payload Type L includes a 64-bit UID, a 16-bit manufacturer, a 16-bithardware type, a 48-bit memory layout, and a variable-length user data,which are transmitted in the order named.

A payload Type M includes a 64-bit UID, a 16-bit manufacturer, a 16-bithardware type, an 8-bit EAC, an 8-bit AFID, an 8-bit SDF, an 8-bit USL,and an 8-bit ASL, which are transmitted in the order named.

A payload Type N includes a 16-bit TID bank length, a variable-lengthTID bank, a 16-bit UII (Unique Item Identifier) length, a 16-bit PC, avariable-length UII or UII set, and a variable-length user data, whichare transmitted in the order named.

A payload Type O includes an 8-bit argument 1 and a 16-bit argument 2,which are transmitted in the order named.

A payload Type P includes a 32-bit access password, a 16-bit UII length,a variable-length UII, a 16-bit new UII length, a variable-length newUII, and a 16-bit PC, which are transmitted in the order named.

A payload Type Q includes a 64-bit UID, a 16-bit start address, a 16-bitlength, and a variable-length user data, which are transmitted in theorder named.

A payload Type R includes a 32-bit access password, a 16-bit UII length,a variable-length UII, a 16-bit start address, a 16-bit length, and avariable-length user data, which are transmitted in the order named.

A payload Type S includes a 64-bit UID, a 48-bit memory layout, a 16-bituser data length, and a variable-length user data, which are transmittedin the order named.

A payload Type T includes a 32-bit access password, a 16-bit UII length,a variable-length UII, a 16-bit new UII length, a variable-length newUII, a 16-bit PC, a 16-bit user data length, a variable-length userdata, a variable-length reserved bank length, and a variable-lengthreserved bank data, which are transmitted in the order named.

A payload Type U includes a 32-bit access password, a 32-bit killpassword, a 16-bit UII length, and a variable-length UII, which aretransmitted in the order named.

A payload Type V includes a 64-bit UID and an 8-bit argument, which aretransmitted in the order named.

A payload Type W includes a 32-bit access password, a 16-bit UII length,a variable-length UII, and a 24-bit lock data, which are transmitted inthe order named.

A payload Type X includes a DR, a 2-bit M, TR, a 2-bit Sel, a 2-bit S,T, a 4-bit Q, and a 3-bit UpDn, which are transmitted in the ordernamed.

The description of the foregoing payload types, the use of each field,and the use method thereof will be described in detail later.

[1.4] Endian Format and Transmission Order Format

All the fields constructing the mobile RFID reader control protocolformat follow the big-Endian format. According to the big-Endian format,the most significant byte value is first written and then the leastsignificant byte value is written. A preamble field, a header field, apayload field, and an end mark field are transmitted in the order named.In the header field, a message type field, a code field, and a payloadlength field are transmitted in the order named. In the payload field, atarget field, an argument type field, a payload data length field, and apayload data and pending field are transmitted in the order named. Ineach field, the most significant byte is first transmitted.

[1.5] Method of Describing Small-size Data in Fixed-size Field

When a small-size data needs to be inserted into a protocol field largerthan the small-sized data, the less significant bytes are first filledand then the remaining more significant bytes are filled with 0x00. Inthis case, the big-Endian format is also applied. For example, when avalue of 12 needs to be inserted into a 16-bit length field, the lesssignificant bytes are filed with 0x0C and the more significant bytes arefilled with 0x00.

[2] Summary and List of Command, Response, and Notification

A protocol between a processor of a mobile terminal and an RFID readercan be classified into a command, a response, and a notification, whichare defined in the ISO and EPC standards.

In the embodiment of the present invention, the command and the responsealways exist and operate in pairs. Only after a response to a commandhas been received, the next command is executed. Each command has aspecific code, which is described in a code field of a header andrepresented in 8 bits. When a response is successful, a code of acorresponding command is described in a code field and aresponse-related content is described in a payload field. On the otherhand, when a response is unsuccessful, a value of 0xFF is described in acode field and a result code is described in a payload field. A payloadvaries according to a command and a response. Detailed types of thepayload will be described in detail later.

[2.1] Command and Response

In the embodiment of the present invention, commands and responses in amobile RFID reader protocol are categorized into readercontrol/management, tag read, tag write, tag lock/unlock, tag kill, andadditional functions. Table 2 below shows an example of a command listaccording to the present invention. In Table 2, the commands areclassified into mandatory commands and optional commands. All thecommands have the corresponding responses. Commands corresponding to atag write category, a tag kill category, and a tag lock category must beimplemented carefully. The reason for this is that such commands maychange the contents of a tag. When these commands are wrongly used,security problems may occur to cause corresponding damages.

TABLE 2 Type Mandatory Command Optional Command Readercontrol/ ReaderPower ControlReader Get Type B A/I Parameters management ConnectionControlGet Reader Information Set Type B A/I category Get SignalStrengthSet Signal ParametersGet Automatic StrengthGet RegionSetRegionReset Read ParametersSet ReaderGet Type C A/I Select ParametersAutomatic Read Set Type C A/I Select Parameters Parameters Get Type CA/I Query-related ParametersSet Type C A/I Query-related Parameters TagRead Type C UII BlockRead Type C User Read Type B TIDRead ReadCategoryDataRead Entire Type C TagStart Type B User DataRead Automatic ReadStopAutomatic Read Entire Type B Tag Tag Write Type B UII SetWriteWriteCategory Type C UII BlockWrite Type B User DataWrite Type C UserDataWrite Entire Type B TagWrite Entire Type C Tag Tag Kill Type C TagKillCategory Tag Lock Type B TagLock LockCategory Type C TagAdditionalFunctionCategory Start Test ModeStop Test ModeStar Get LastResult Receive TestStop Receive Test

[2.2] Mobile RFID Reader Control/Management Category

An RFID reader control/management command category includes commandsshown in Table 3 below. The main commands relate to reader powercontrol, reader connection control, get reader information, reader RFsignal strength control, and reader filter function control. The readerpower control command and the reset reader command, which are the mostbasic reader control commands, may be directly controlled by a hardwareinterface such as GIPO. In this case, the foregoing two commands may notbe implemented separately.

TABLE 3 Code Value Command Name (Hexadecimal) Description of CommandReader Power 0x01 Power on/off reader (Active/Sleep) Control Reader 0x02Initialize or end communication with reader Connection Control GetReader Information 0x03 Get reader-related information (Reader at leasthave information about model, manufacturer, S/ N, usable frequency, andsupportable tag type) Get Signal 0x04 Get RF signal strength of readerStrength Set Signal 0x05 Set RF signal strength of reader Strength GetRegion 0x06 Get nation/region information of reader Set Region 0x07 Setnation/region information of reader Reset Reader 0x08 Immediately endall operations of reader and initialize reader. Thereafter, readercontrol requires using Reader connection control command Get Type B A/I0x09 Get air interface parameters related to Type B Parameters standardSet Type B A/I 0x0A Set air interface parameters related to Type BParameters standard Get Type C A/I 0x0B Get select parameters of airinterface related to Select Parameters Type C standard Set Type C A/I0x0C Set select parameters of air interface related to Select ParametersType C standard Get Type C A/I 0x0D Get query-related parameters of airinterface Query related related to Type C standard Parameters Set Type CA/I 0x0E Set query-related parameters of air interface Query relatedrelated to Type C standard Parameters Get Automatic 0x0F Get parametersrelated to automatic mode read read Parameters Set Automatic 0x10 Setparameters related to automatic mode read read Parameters VendorSpecific 0x11-0x17 Vendor can be defined Reserved 0x18-0x1F reserved

Referring to Table 3, the reader control/management category includes aget automatic read parameters command and a set automatic readparameters command for getting and setting commands related to anautomatic read command. These commands operate according to presetparameters. These preset parameters include a read cycle indicating thenumber of times of performance of a read operation, and also include aread delay time indicating a delay time between read operations when thereader performs a read operation more than two times.

[2.3] Tag Read Category

A tag read category includes commands shown in Table 4 below. Thesecommands are mainly used to read the specific ID of a tag (TID), a UIIset (e.g., mCodes of MRF and EPC codes indicating things), and a usermemory bank area.

TABLE 4 Code Value Command Name (Hexadecimal) Description of CommandRead Type B TID 0x21 Read 8th through 16th address values and TID of ISO18000-6B Tag Read Type C UII 0x22 Read UII block of ISO 18000-6C TagBlock (UII or UII Set and PC are readed) Read Type B 0x23 Read usermemory bank of ISO User Data 18000-6B Tag Read Type C 0x24 Read usermemory bank of ISO User data 18000-6C Tag Read Entire Type 0x25 Read allarea of ISO 18000-6B Tag B Tag Read Entire Type 0x26 Read all area ofISO 18000-6C Tag C Tag Start Automatic 0x27 Perform automatic mode readRead operation (applicable to the above 6 commands) Stop Automatic 0x28Stop automatic mode read operation Read Vendor Specific 0x29-0x37 Vendorcan be defined Reserved reserved

Referring to Table 4, the tag read category further includes commandsfor automatically reading a plurality of successive tags. The commandsrelated to the automatic read operation include a start automatic readcommand and a stop automatic read command.

The start automatic read command is configured to designate codes(0x21˜0x26) of read commands to be repeated and a repeat cycle, whichindicates which number of times a read operation of a read cycledesignated in the set automatic read parameters command needs to berepeated. That is, the total number of times of a read operation of theRFID reader equals Read cycle×Repeat cycle. When a repeat cycle is aninvalid value, a response indicating a wrong value is generated in aresult code. When a read operation has been performed by the repeatcycle or there is no tag to be read, the RFID reader automatically stopsa read operation.

The stop automatic read command is used to stop the read operation thatis being performed by the start automatic read command.

Most commands cannot be executed during the automatic read operation. Ifsuch a command is to be executed, the command is regarded as failed andthe result code receives 0x0D of Automatic Read in Operation. Examplesof commands executable during the automatic read operation are resetreader, get signal strength, set signal strength, and stop automaticread.

Data obtained from an RFID tag by a tag read command are transmitted tothe processor of the terminal through a notification or a response to acommand. In the embodiment of the present invention, a buffer functionof storing data obtained from a tag by a reader chip is set to beoptional. However, when the buffer function needs to be implemented, avendor-specific command code area of the additional function categorymust be used and the implementation must be based on the HAL APIstandards.

[2.4] Tag Write Category

A tag write category includes commands shown in Table 5 below. Thesecommands are used to write an ID code, a user memory bank area, andadditional information in the tag.

TABLE 5 Code Value Command Name (Hexadecimal) Description of CommandWrite Type C UII 0x41 Write UII block of ISO 18000-6C Block Tag (UIIset, PC and CRC values must be written) Write Type B User 0x42 Writeuser memory bank area of Data ISO 18000-6B Tag Write Type C User 0x43Write user memory bank area of Data ISO 18000-6C Tag Write Entire Type0x44 Write entire content of ISO B Tag 18000-6B Tag Write Entire Type0x45 Write entire content of ISO C Tag 18000-6C Tag Vendor Specific0x46-0x57 Vendor can be defined Reserved 0x58-0x5F reserved

[2.5] Tag Kill Category

A tag kill category includes commands shown in Table 6 below. Thesecommands are used to kill (erase) the contents of a tag.

TABLE 6 Code Value Command Name (Hexadecimal) Description of CommandKill Type c Tag 0x61 Kill Type C Tag Vendor Specific 0x62-0x77 Vendorcan be defined Reserved 0x78-0x7F reserved

[2.6] Tag Lock Control Category

A tag lock control category includes commands for controlling a lockfunction for preventing the contents of a tag to be changed or erased,which are shown in Table 7 below.

TABLE 7 Code Value Command Name (Hexadecimal) Description of CommandLock Type B Tag 0x81 Control lock of ISO1800-6B Tag Lock Type C Tag 0x82Control lock of ISO 1800-6C Tag Vendor Specific 0x83-0x97 Vendor can bedefined Reserved 0x98-0x9F reserved

A lock command is configured such that different commands are assignedto tags.

Also, arguments necessary for the lock command are based on the airinterface standards.

[2.7] Additional Function Category

An additional function category includes commands for additionalfunctions, which are shown in Table 8 below.

TABLE 8 Code Value Command Name (Hexadecimal) Description of Command GetLast Result 0xA1 Reader gets the last event Stat Test Mode 0xA2 Convertmode of reader into test mode Stop Test Mode 0xA3 Stop test mode ofreader Stat Receive Test 0xA4 Start count of successfully-received airinterface packet to measure receive sensitivity Stop Receive Test 0xA5Stop count of successfully-received air interface packet for measurementof receive sensitivity Vendor Specific 0xA6-0xB7 Vendor can be definedReserved 0xB8-0xFE reserved

The additional function category includes convenience-providingfunctions other than basic contents for processing a tag by the reader.These include a filter function of the reader and commands for gettingand setting the tag access status of the reader. The additional functioncategory further includes commands for starting or ending a test mode. Astart receive test command and a stop receive test command formeasurement of receive sensitivity can be used only in the test mode.The test mode will be described in detail later.

[2.8] Result Code

A result code is used for a response to a command. The result codeindicates results of both success and failure. For the case of Success,a code value of a corresponding command is inserted into the code fieldof the header of a response protocol message. For the case of Failure, avalue of 0xFF is inserted. Also, an 8-bit result code is inserted into apayload data section. This facilitates discrimination between contentsof errors when commands are incorrectly executed. A result code 0x00indicates success, which is used in case that no separate result valueexists when a command is successful. Table 9 below illustrates the typesof results and corresponding codes.

TABLE 9 Error Type Error Code Description Success 0x00 Indicates successof command Power Control Failure 0x01 Power control on/off operation isfailed Connection control 0x02 Connection control operation is failedFailure Cannot Get Reader Info 0x03 Reader ID cannot be set or gotCannot Get Signal 0x04 Signal strength cannot be got Strength SignalStrength Control 0x05 Signal strength cannot be set Failure ReaderFilter Control 0x06 Reader Filter cannot be control Failure Cannot GetRegion 0x07 Region information of reader cannot be got Region controlFailure 0x08 Region of reader cannot be set Read Failure 0x09 Readoperation is failed Automatic Read Failure 0x0A Automatic mode readoperation is failed Automatic Read in 0x0B Automatic read is already inoperation Operation Cannot Stop Automatic 0x0C Automatic mode readcannot be stopped Read Not in Automatic Mode 0x0D Automatic read is notin operation Invalid Parameter 0x0E Parameter is invalid Cannot GetAutomatic 0x0F Automatic mode parameters cannot be got Parameters WriteFailure 0x10 Write operation is failed Erasure Failure 0x11 Eraseoperation is failed Kill Failure 0x12 Kill operation is failed LockControl Failure 0x13 Lock operation is failed Cannot Get Last Result0x14 Last event cannot be got No Tag Detected 0x15 No tag is detectedPassword not Match 0x16 Password does not match Not Supported 0x17Command is not supported Command Undefined command 0x18 Command is notdefined Cannot Reset Reader 0x19 Reader cannot be reset Cannot ControlType B 0x1A Air interface parameters related to Type B A/I Parametersstandard cannot be set or got Cannot Control Type C 0x1B Air interfaceparameters related to Type C A/I Parameters standard cannot be set orgot No User Data 0x1C User memory bank does not exist Reader is not inTest 0x1D Reader is not in current test mode Mode Test Mode Control 0x1ETest mode control is failed Failure Automatic Read 0x1F Automatic readis completed Complete No more Tags to Read 0x20 No more tags remain tobe red Vendor Specific 0x30-0xDF Reserved 0xE0-0xFF

[2.9] Vendor-Specific Command and Response

In addition to the commands proposed in the present invention,vendor-specific commands of an RFID reader manufacturer may be furtherincluded in all the categories described above. Preferably, thesevendor-specific commands use code values of a vendor-specific area inaccordance with the categories proposed in the present invention. Forexample, when a specific command corresponding to a tag read functionneeds to be added, it preferably uses a code value of 0x29˜0x37 that isa vendor-specific area of a tag read category.

[2.10] Notification

A notification is a protocol message that is transmitted from the RFIDreader to the processor of the terminal. Unlike a response message, thenotification protocol message is independent of a command. Thenotification is mainly used as a response for indicating a result for anoperation repeated in an automatic mode, and is used for critical errorsgenerated in the RFID reader.

In the embodiment of the present invention, the notification protocolmessage may have the same format as the response protocol message.However, for example, a value of 0x02 may be used in a message typefield to discriminate the notification protocol message from theresponse protocol message.

In addition, when a critical error is generated in the reader, thenotification may be used to inform the processor of the error. In thiscase, a format may be identical to that of a command containing theerror, which is identical to what is designated as a notification in amessage type field. The critical errors are not defined in the presentinvention, but may be those defined by a vendor. An error that needs tobe transmitted by a notification may be defined using a vendor-specificarea of a result code.

[2.11] Compatibility with HAL API Standards

Tables 10 and 11 below show relationships between commands defined inthe HAL API standards and the mobile reader protocol commands proposedin the present invention. One HAL API command may correspond to severalof the mobile reader protocol commands, and vice versa. A driver must beimplemented in accordance with the relationships.

For example, a MH_rfidReportReaderStatus command is implemented using aconsiderably large number of mobile reader protocol commands. In thiscase, the implemented is preferably made by including a status parameterin the driver. When the results of a performed mobile reader protocolare stored in the status parameter, it is possible to reduce the numberof reader protocol commands that needs to be performed when theMH_rfidReportReaderStatus command is received. In addition, since areturn value for an HAL API function must be given, the correspondingresults must be stored in the status parameter.

Among the HAL API commands, commands related to control of a buffer andmanagement of a filter may be selectively implemented. The presentinvention assumes that the buffer and the filter may exist in any one ofthe HAL or the mobile reader chip. Accordingly, in order to implement abuffer function or a filter function in a reader chip, a mobile readerprotocol command must be implemented such that the relationship with anHAL API command is proper. In this case, the mobile reader protocol mayuse a code value of a vendor-specific command field.

TABLE 10 HAL API Standard Type Command Mobile Reader Protocol StandardCommand ReaderMH_rfidPowerOnMH_rfidPowerOffMH_rfidOpenReaderMH_rfidCloseReaderMH_(—)Reader Power ControlReader Power Control ControlrfidResetReaderMH_rfidSetRegionMH_rfidGetRegionMH_rfidSetRFStrengthMH_(—)Reader Connection ControlReaderrfidGetRFStrengthMH_rfidGetManufacturerMH_rfidGetModelMH_rfidisOpenReaderMH_(—)Connection controlReset ReaderReaderrfidisBusyReaderMH_rfidSetQMH_rfidGetQMH_rfidSetReadCycleMH_(—)Connection ControlSet RegionGet RegionSetrfidGetReadCycleMH_rfidSetReadDelaytimeMH_rfidGetReadDelaytime SignalStrengthGet Signal StrengthGet Reader InfoGet Reader InfoProcess indriver: Response to Reader Connection ControlProcess in driver: Check ofautomatic reading or notSet Type C A/I Query Related ParametersGet TypeC A/I Query Related ParametersSet Automatic Read ParametersGet AutomaticRead ParametersSet Automatic Read ParametersGet Automatic ReadParameters

TABLE 11 HAL API Standard Type Command Mobile Reader Protocol StandardCommand TagControlMH_rfidReadTIDCMH_rfidReadUIISetCMH_rfidReadUIIBlockCMH_(—) Read Type CUII BlockRead Type C UIIrfidReadUserDataCMH_rfidStopReadMH_rfidReadUIISetBMH_(—) BlockRead TypeC UII BlockRead Type CrfidReadUserDataBMH_rfidWriteUserDataBMH_rfidLockBMH_(—) User DataStopAutomatic ReadRead Type BrfidWriteUIISetCMH_rfidWriteUIIBlockCMH_rfidWriteUserDataCMH_(—) UserDataRead Type B User DataWrite rfidLockCMH_rfidUnlockCMH_rfidKillTagCType B User DataLock Type B TagWrite Type C UII BlockWrite Type C UIIBlockWrite Type C User DataLock Type C TagLock Type C TagKill Type C TagBufferControlMH_rfidCreateBufferMH_rfidDestroyBufferMH_rfidReadBufferMH_(—) Cannot besupported by mobile readerrfidWriteBufferMH_rfidDeleteBufferMH_rfidClearBufferMH_(—) protocol butcan be implemented in vendor-rfidGetNumBufferMH_rfidGetMaxNumBufferMH_rfidSortBufferMH_(—) specificfashion rfidValidateBuffer FilterControlMH_rfidAddFilterMH_rfidDeleteFilterMH_rfidEnableFilterMH_(—) Cannot besupported by mobile reader rfidDisableFilter protocol but can beimplemented in vendor- specific fashion StatusReportMH_rfidReportReaderStatus Process in reader: Status parameters arestored and processed in case of Power and OpenGet Automatic ReadParametersGet RegionGet Signal StrengthGet Reader InformationGet Type CA/I Query Related Parameters

[3] Details of Command, Response, and Notification

This section [3] describes details of the commands, the responses, andthe notifications that are stated above. The following descriptionsillustrate arguments needed by the commands and the responses, theirtypes, and notifications. Also illustrated are the relationship betweenthe abovementioned protocol format and the command/response/thenotification, and protocol streams for representing them.

[3.1] Reader Control/Management Category

[3.1.2] Reader Power Control

A reader power control command is used to control turning on/off powersupplied to the hardware of the RFID reader. Power is supplied to thereader in the on state, while no power is supplied to the reader in theoff state.

The reader power control command is constructed to include a messagetype, a code, a payload type, and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0x01 indicating reader power control. The payload type may berepresented by Payload Type A. The argument is 8-bit power stateinformation, which may be represented by 0xFF in an on state and by 0x00in an off state.

FIG. 7 illustrates the structure of a protocol message in a power onstate. Specifically, FIG. 7 illustrates values of a preamble field, amessage type field, a code field, a payload field MSB, a payload fieldLSB, an argument field, and an end mark field.

A response to the reader power control command is constructed to includea message type, a code, a payload type, and an argument. The messagetype may be represented by 0x01 indicating a response. The code may berepresented by 0x01 for the case of Success, and by 0xFF for the case ofFailure. The payload type may be represented by Payload Type A. Theargument may be represented by a result code 0x00 indicating success andby a result code 0x01 indicating power control failure.

FIG. 8 illustrates the structure of a protocol message for a readerpower control response for the case of Success. Specifically, FIG. 8illustrates values of a preamble field, a message type field, a codefield, a payload field MSB, a payload field LSB, an argument field, andan end mark field.

[3.1.2]Reader Connection Control

A reader connection control command is used to connect/disconnect theprocessor to/from the reader. When the processor is connected to thereader, the reader can receive and process all commands. On the otherhand, when the processor is disconnected from the reader, the reader canprocess only power/connection control commands. When the reader wassupplied with power but cannot be connected, the minimum power issupplied.

The reader connection control command is constructed to include amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x00 indicating a command. The code may berepresented by 0x02 indicating reader connection control. The payloadtype may be represented by Payload Type A. The argument is 8-bit readerconnection state information, which may be represented by 0xFF in caseof connection and by 0x00 in case of disconnection.

FIG. 9 illustrates the structure of a protocol message in a connectionstate. Specifically, FIG. 9 illustrates values of a preamble field, amessage type field, a code field, a payload field MSB, a payload fieldLSB, an argument field, and an end mark field.

A response to the reader connection control command is constructed toinclude a message type, a code, a payload type, and an argument. Themessage type may be represented by 0x01 indicating a response. The codemay be represented by 0x02 in case of Success, and by 0xFF in case ofFailure. The payload type may be represented by Payload Type A. Theargument may be represented by a result code 0x00 indicating success andby a result code 0x02 indicating Connection Control Failure.

FIG. 10 illustrates the structure of a protocol message for a readerconnection control response for the case of Success. Specifically, FIG.10 illustrates values of a preamble field, a message type field, a codefield, a payload field MSB, a payload field LSB, an argument field, andan end mark field.

[3.1.3] Command for Getting Information of the Reader (Get ReaderInformation)

A get reader Information command is used to get information from thereader. The information includes a model name, an S/N, a manufacturer, ause frequency, and the type of a tag supported.

The get reader information control command is constructed to include amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x00 indicating a command. The code may berepresented by 0x03 indicating the get reader information command. Thepayload type may be represented by Payload Type A. The argument is an8-bit information type data indicating the type of information to berequested from the reader, which may include a reader model name (0x00),a reader S/N (0x01), a reader manufacturer (0x02), a reader usefrequency (0x03), and the type (0x04) of a tag supported by the reader.

FIG. 11 illustrates the structure of a protocol message when the readermanufacturer is requested. Specifically, FIG. 11 illustrates values of apreamble field, a message type field, a code field, a payload field MSB,a payload field LSB, an argument field, and an end mark field.

A response to the get reader information command is constructed toinclude a message type, a code, a payload type, and an argument. Themessage type may be represented by 0x01 indicating a response. The codemay be represented by 0x03 in case of Success, and by 0xFF in case ofFailure. The payload type may be represented by Payload Type B in caseof model name, S/N, manufacturer and frequency, by Payload Type A incase of the tag type supported by the reader, and by Payload Type A incase of command failure. The argument may be represented by avariable-length corresponding string in case of model name, S/N,manufacturer and frequency, by an 8-bit value 00000001 (ISO 18000-6B) or00000010 (ISO 18000-6C) in case of the tag type supported by the reader,by ‘Bit OR’ in case of supporting plurality, and by a result code 0x03indicating Cannot Get Reader Info in case of command failure.

FIG. 12 illustrates the structure of a protocol message for a get readerinformation response when the manufacture is ‘LC ELECTRONICS’.Specifically, FIG. 12 illustrates values of a preamble field, a messagetype field, a code field, a payload field MSB, a payload field LSB, anargument field, and an end mark field. FIG. 13 illustrates a responsewhen the tag type supported by the reader is 18000-B/C.

[3.1.4] Command for Getting an RF Signal Strength of the Reader (GetSignal Strength)

A get signal strength command is used to get a currently-set RF signalstrength of an RFID reader. The signal strength can be represented inpercentage, and the maximum signal strength the reader can provide canbe regarded as 100%.

The get signal strength command includes a message type and a code, butdoes not include a payload type and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0x04 indicating Get Signal Strength.

FIG. 14 illustrates the structure of a protocol message for a get signalstrength command. Specifically, FIG. 14 illustrates values of a preamblefield, a message type field, a code field, a payload field MSB, apayload field LSB, and an end mark field.

A response to the get signal strength command is constructed to includea message type, a code, a payload type, and an argument. The messagetype may be represented by 0x01 indicating a response. The code may berepresented by 0x04 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A. The argument maybe represented by 0˜100 (0x00˜0x64) indicating the signal strength inpercentage, and by a result code 0x04 indicating Cannot Get SignalStrength.

FIG. 15 illustrates the structure of a protocol message for a Get SignalStrength response for the case of Success when the signal strength is75%. Specifically, FIG. 15 illustrates values of a preamble field, amessage type field, a code field, a payload field MSB, a payload fieldLSB, an argument field, and an end mark field.

[3.1.5] Command for Setting an RF Signal Strength of the Reader (SetSignal Strength)

A set signal strength command is used to set an RF signal strength ofthe reader. The signal strength can be represented in percentage, andthe maximum signal strength the reader can provide can be regarded as100%.

The set signal strength command includes a message type, a code, apayload type, and an argument. The message type may be represented by0x00 indicating a command. The code may be represented by 0x05indicating Set Signal Strength. The payload type may be represented byPayload Type A. The argument may be represented by 0x00˜0x64 (0˜100)indicating an 8-bit signal strength value.

FIG. 16 illustrates the structure of a protocol message for a set signalstrength command when the signal strength is 50%. Specifically, FIG. 16illustrates values of a preamble field, a message type field, a codefield, a payload field MSB, a payload field LSB, an argument field, andan end mark field.

A response to the set signal strength command is constructed to includea message type, a code, a payload type, and an argument. The messagetype may be represented by 0x01 indicating a response. The code may berepresented by 0x05 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A. The argument maybe represented by a result code 0x00 indicating success, and by a resultcode 0x04 indicating Signal Strength Control Failure.

FIG. 17 illustrates the structure of a protocol message for a get SignalStrength response for the case of Success. Specifically, FIG. 17illustrates values of a preamble field, a message type field, a codefield, a payload field MSB, a payload field LSB, an argument field, andan end mark field.

[3.1.6] Command for Getting Region/Nation Information Set in the Reader(Get Region)

A get region command is used to get region/nation information set in thereader. That is, since the radio wave standard the RFID reader can useis different according to nations and regions, the get region command isused to get such region/nation information.

The get region command includes a message type and a code, but does notinclude a payload type and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0x06 indicating Get Region.

FIG. 18 illustrates the structure of a protocol message for the getregion command. Specifically, FIG. 18 illustrates values of a preamblefield, a message type field, a code field, a payload field MSB, apayload field LSB, and an end mark field.

A response to the get region command is constructed to include a messagetype, a code, a payload type, and an argument. The message type may berepresented by 0x01 indicating a response. The code may be representedby 0x06 in case of Success, and by 0xFF in case of Failure. The payloadtype may be represented by Payload Type A. The argument may berepresented by an 8-bit value indicating a region or a nation set in thereader, and by a result code 0x07 indicating Cannot Get Region. Forexample, Korea, America, Europe, Japan, and China may be represented by0x01, 0x02, 0x04, 0x08, and 0x10, respectively.

FIG. 19 illustrates the structure of a protocol message for a get regionresponse when a region set in the reader is Korea. Specifically, FIG. 19illustrates values of a preamble field, a message type field, a codefield, a payload field MSB, a payload field LSB, an argument field, andan end mark field.

[3.1.7] Command for Setting Region/Nation Information in the Reader (SetRegion)

A set region command is used to set region/nation information in thereader. That is, since the radio wave standard the RFID reader can useis different according to nations and regions, the set region command isused to set such region/nation information.

The set region command includes a message type, a code, a payload type,and an argument. The message type may be represented by 0x00 indicatinga command. The code may be represented by 0x07 indicating Set Region.The payload type may be represented by an 8-bit value indicating aregion set in the reader, which is identical to that of Get Region.

FIG. 20 illustrates the structure of a protocol message for the setregion command when a nation set in the reader is Korea, which mayinclude values of a preamble field, a message type field, a code field,a payload field MSB, a payload field LSB, an argument field, and an endmark field.

A response to the set region command is constructed to include a messagetype, a code, a payload type, and an argument. The message type may berepresented by 0x01 indicating a response. The code may be representedby 0x07 in case of Success, and by 0xFF in case of Failure. The payloadtype may be represented by Payload Type A. The argument may berepresented by a result code 0x00 indicating success and by a resultcode 0x08 indicating Region Control Failure.

FIG. 21 illustrates the structure of a protocol message for a set regionresponse when a region set in the reader is Korea. Specifically, FIG. 21illustrates values of a preamble field, a message type field, a codefield, a payload field MSB, a payload field LSB, an argument field, andan end mark field.

[3.1.8] Reset Reader

A reset reader command is used to promptly stop all operations of thereader and initialize the reader. Upon completion of the initialization,a response to the reset reader command is transmitted to the reader.Right after execution of the reset reader command, the aforementionedreader connection control command must be used to connect the readersince the reader is initialized to a state where only power is supplied.

The reset reader command includes a message type and a code, but doesnot include a payload and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0x08 indicating Reset Reader.

FIG. 22 illustrates the structure of a protocol message for the resetreader command, which may include values of a preamble field, a messagetype field, a code field, a payload field MSB, a payload field LSB, andan end mark field.

A response to the reset reader command is constructed to include amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0x08 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A. The argument maybe represented by a result code 0x00 indicating success and by a resultcode 0x19 indicating Cannot Reset Reader.

FIG. 23 illustrates the structure of a protocol message for a responseto the reset reader command in case of Success. Specifically, FIG. 23illustrates values of a preamble field, a message type field, a codefield, a payload field MSB, a payload field LSB, an argument field, andan end mark field.

[3.1.9] Command for Getting Air Interface Parameters (Get Type B A/IParameters)

A get type B A/I parameters command is used to get air interface (A/I)parameters related to the ISO 18000-6B standards. For example, these A/Iparameters may be an modulation index (MI), a byte mask (BM), and anaddress. The get type B A/I parameters command includes a message typeand a code, but does not include a payload type and an argument. Themessage type may be represented by 0x00 indicating a command. The codemay be represented by 0x09 indicating Get Type B A/I Parameters. FIG. 24illustrates the structure of a protocol message for the get type B A/Iparameters command, which includes values of a preamble field, a messagetype field, a code field, a payload field MSB, a payload field LSB, anargument, and an end mark field.

A response to the get type B A/I parameters command is constructed toinclude a message type, a code, a payload type, and an argument. Themessage type may be represented by 0x01 indicating a response. The codemay be represented by 0x09 in case of Success, and by 0xFF in case ofFailure. The payload type may be represented by Payload Type C in caseof Success, and by Payload Type A in case of Failure.

In case of Success, the argument represents a modulation index, a bytemask, and an address. The modulation index may be represented by an8-bit value, which determines the ISO 18000-6B modulation scheme. Thatis, MI=18% (0x00), MI=100% (0xFF), and the like are represented. Thebyte mask may be represented by an 8-bit value, which is an 8-bit bytemask value defined in the ISO 18000-6B standards to determine which bitof one byte is compared. The address may be represented by an 8-bitvalue, which is an address defined in the ISO 18000-6B standards todetermine which portion of a tag is compared. In case of Failure, theaddress may be represented by a result code 0x1A indicating CannotControl Type B A/I Parameters and a result code 0x17 indicating NotSupported Command.

FIG. 25 illustrates the structure of a response protocol message for theget type B A/I parameters command. Here, MI=18%, BM=0xFF, andAddress=0xFF.

[3.1.10] Command for Setting A/I Parameters (Set Type B A/I Parameters)

A set type B A/I parameters command is used to A/I parameters related tothe ISO 18000-6B standards. The set type B A/I parameters commandincludes a message type, a code, a payload type, and an argument. Themessage type may be represented by 0x00 indicating a command. The codemay be represented by 0x0A indicating Set Type B A/I Parameters. Thepayload type may be represented by Payload Type C.

The argument represents a modulation index, a byte mask, and an address.The modulation index may be represented by an 8-bit value, whichdetermines the ISO 18000-6B modulation scheme. That is, MI=18% (0x00),MI=100% (0xFF), and the like are represented. The byte mask may berepresented by an 8-bit value, which is an 8-bit byte mask value definedin the ISO 18000-6B standards to determine which bit of one byte iscompared. The address may be represented by an 8-bit value, which is anaddress defined in the ISO 18000-6B standards to determine which portionof a tag is compared.

FIG. 26 illustrates the structure of a protocol message for the set typeB A/I parameters command, wherein MI=18%, BM=0xFF, and Address=0xFF.

A response to the set type B A/I parameters command includes a messagetype, a code, a payload type, and an argument. The message type may berepresented by 0x01 indicating a response. The code may be representedby 0x0A in case of Success, and by 0xFF in case of Failure. The payloadtype may be represented by Payload Type A.

The argument may be represented by a result code 0x00 in case ofSuccess, by a result code 0x1A in case of Cannot Control Type B A/IParameters, and by 0x17 in case of Not Supported Command.

FIG. 27 illustrates the structure of a response protocol message for thecase of Success.

[3.1.11] Command for Getting A/I Select Parameters (Get Type C A/ISelect Parameters)

A get type C A/I select parameters command is used to get A/I selectparameters related to the ISO 18000-6C standards. The get type C A/Iselect parameters command includes a message type and a code, but doesnot include a payload type and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0x0B indicating Get Type C A/I Select Parameters.

FIG. 28 illustrates the structure of a protocol message for the get typeC A/I select parameters command.

A response to the get type C A/I select parameters command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0x0B in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type D, and by PayloadType A in case of Failure.

In case of Failure, the argument may be represented by a result code0x1B. In case of Success, the argument may be represented by a 3-bittarget value to which a parameter is applied [Inventoried S0(000),Inventoried S1(001), Inventoried S2(010), Inventoried S3(011), SL(100)],a 3-bit action value defined in Type C, a 2-bit value indicating amemory bank of a tag [RFU(00), UII(01), TID(10), User(11)], a 32-bitstart (or bit) address pointer of a tag memory to be compared, an 8-bitlength value of the tag memory to be compared, a 1-bit truncated flagrepresenting Enable(1) and Disable(0), a 7-bit RFU (Reserved forFurther) (use a reserved value of 0000000), and a bit mask (0˜255 bit)defined in Type C.

FIG. 29 illustrates the structure of a response protocol message to theGet Type C A/I Select Parameters command in case that Target=S0,Action=assert SL or inventoried->A, MB=User, Pointer=0x000000FF,Length=0x20, T=0, and Mask=11111111111111110000000000000000.

[3.1.12] Command for Setting A/I Select Parameters (Set Type C A/ISelect Parameters)

A set type C A/I select parameters command is used to set A/I selectparameters related to the ISO 18000-6C standards. The set type C A/Iselect parameters command includes a message type, a code, a payloadtype, and an argument.

The message type may be represented by 0x00 indicating a command. Thecode may be represented by 0x0C indicating Set Type C A/I SelectParameters. The payload type may be represented by Payload Type D.

The argument may be represented by a 3-bit target value to which aparameter is applied [Inventoried S0(000), Inventoried S1(001),Inventoried S2(010), Inventoried S3(011), SL(100)], a 3-bit action valuedefined in Type C, a 2-bit value indicating a memory bank of a tag[RFU(00), UII(01), TID(10), User(11)], a 32-bit start (or bit) addresspointer of a tag memory to be compared, an 8-bit length value of the tagmemory to be compared, a 1-bit truncated flag representing Enable(1) andDisable(0), a 7-bit RFU (use a reserved value of 0000000), and a bitmask (0˜255 bit) defined in Type C.

FIG. 30 illustrates the structure of a protocol message for the set typeC A/I select parameters command in case that Target=S0, Action=assert SLor inventoried->A, MB=User, Pointer=0x000000FF, Length=0x20, T=0, andMask=11111111111111110000000000000000.

A response to the set type C A/I select parameters command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0x0C in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A.

The argument may be represented by a result code 0x00 in case ofSuccess, and by a result code 0x1B in case of Cannot Control Type C A/IParameters.

FIG. 31 illustrates the structure of a response protocol message to theSet Type C A/I Select Parameters command.

[3.1.13] Command for Getting A/I Query-Related Parameters (Get Type CA/I Query-Related Parameters)

A get type C A/I query-related parameters command is used to get A/Iquery-related parameters related to the ISO 18000-6C standards.

The get type C A/I query-related parameters command includes a messagetype and a code, but does not include a payload type and an argument.The message type may be represented by 0x00 indicating a command. Thecode may be represented by 0x0D indicating Get Type C A/I Query-relatedParameters. FIG. 32 illustrates the structure of a protocol message forthe get type C A/I query-related parameters command.

A response to the get type C A/I query-related parameters commandincludes a message type, a code, a payload type, and an argument. Themessage type may be represented by 0x01 indicating a response. The codemay be represented by 0x0D in case of Success, and by 0xFF in case ofFailure. The payload type may be represented by Payload Type E in caseof Success, and by Payload Type A in case of Failure. In case of CannotControl Type C A/I Parameters, the argument may be represented by aresult code 0x1B.

In case of Success, the argument may be represented by a 1-bit valueindicating DR (TRcal divide ratio) (if DR is 8 or 64/3, the 1-bit valueis set to ‘0’ or ‘1’, respectively), a 2-bit value M indicating thenumber of cycles per symbol (if the number of cycles is 1, 2, 4, or 8, Mis set to ‘00’, ‘01’, ‘10’, or ‘11’, respectively), a 1-bit Trex value(if Pilot Tone exists, the value is set to ‘1’; if not, the value is setto ‘0’), a 2-bit Sel value (A11:‘00’ or ‘01’; ˜SL:‘10’; and SL:‘11’), a2-bit session value (S0:‘00’; 51:‘01’; S2:‘10’; and S3:‘11’), a 1-bittarget value (A:‘0’; and B: ‘1’), a 4-bit value Q indicating the numberof slots per round, and a 3-bit UpDn value (if Q is unchanged, it is setto ‘000’; if Q=Q+1, Q is set to ‘110’; and if Q=Q−1, Q is set to ‘011’).

FIG. 33 illustrates the structure of a response protocol message to theget type C A/I query-related parameters command for the case where DR=8,M=1, Trex=no pilot tone, Sel=A11, Session=S0, Target=A, Q=8, andUpDn=not changed.

[3.1.14] Command for Setting A/I Query-Related Parameters (Set Type CA/I Query-Related Parameters)

A set type C A/I query-related parameters command is used to set A/Iquery-related parameters related to the ISO 18000-6C standards.

The set type C A/I query-related parameters command includes a messagetype, a code, a payload type, and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0x0E indicating Set Type C A/I Query-related Parameters. The payloadtype may be represented by Payload Type E. The argument may berepresented by a 1-bit value indicating DR (TRcal divide ratio) (if DRis 8 or 64/3, the 1-bit value is set to ‘0’ or ‘1’, respectively), a2-bit value M indicating the number of cycles per symbol (if the numberof cycles is 1, 2, 4, or 8, M is set to ‘00’, ‘01’, ‘10’, or ‘11’,respectively), a 1-bit Trex value (if Pilot Tone exists, the value isset to ‘1’; if not, the value is set to ‘0’), a 2-bit Sel value (A11:‘00’ or ‘01’; ˜SL:‘10’; and SL:‘11’), a 2-bit session value (S0:‘00’;S1:‘01’; S2:‘10’; and S3:‘11’), a 1-bit target value (A:‘0’; and B:‘1’), a 4-bit value Q indicating the number of slots per round, and a3-bit UpDn value (if Q is unchanged, it is set to ‘000’; if Q=Q+1, Q isset to ‘110’; and if Q=Q−1, Q is set to ‘011’).

FIG. 34 illustrates the structure of a protocol message for the set typeC A/I query-related parameters command for the case where DR=8, M=1,Trex=no pilot tone, Sel=A11, Session=S0, Target=A, Q=8, and UpDn=notchanged.

A response to the set type C A/I query-related parameters commandincludes a message type, a code, a payload type, and an argument. Themessage type may be represented by 0x01 indicating a response. The codemay be represented by 0x0E in case of Success, and by 0xFF in case ofFailure. The payload type may be represented by Payload Type A. Theargument may be represented by a result code 0x00 in case of Success,and by a result code 0x1B in case of Cannot Control Type C A/IParameters.

FIG. 35 illustrates the structure of a response protocol message to theset type C A/I query-related parameters command.

[3.1.15] Command for Getting Automatic Tag Read Parameters (GetAutomatic Read Parameters)

A get automatic read parameters command is used to get automatic tagread parameters.

The get automatic read parameters command includes a message type and acode, but does not include a payload type and an argument. The messagetype may be represented by 0x00 indicating a command. The code may berepresented by 0x1F indicating Get Automatic Read Parameters. FIG. 36illustrates the structure of a protocol message for the get automaticread parameters (Read Entire Type A Tag) command.

A response to the get automatic read parameters command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0x0F in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type F in case ofSuccess, and by Payload Type A in case of Failure. In case of Success,the argument may include a 16-bit read cycle value indicating the numberof times of read operation performed by the reader, and an 8-bit readdelay time value representing a delay (msec) between read operationsperformed by the reader. In case of Cannot Get Automatic Parameters, theargument may include a result code 0x0F. In case of Not SupportedCommand, the payload may include a result code 0x17. FIG. 37 illustratesthe structure of a response protocol message to the set automatic readparameters command for the case where Read Cycle=50, and Read DelayTime=50 msec.

[3.1.16] Command for Setting Automatic Tag Read Parameters (SetAutomatic Read Parameters)

A set automatic read parameters command is used to set automatic readparameters.

The set automatic read parameters command includes a message type, acode, a payload type, and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0x10 indicating Set Automatic Read Parameters. The payload type may berepresented by Payload Type F. The argument may include a 16-bit readcycle value indicating the number of times of read operation performedby the reader, and an 8-bit read delay time value representing a delay(msec) between read operations performed by the reader. FIG. 38illustrates the structure of a protocol message for the set automaticread parameters command for the case where Read Cycle=50, and Read DelayTime=50 msec.

A response to the set automatic read parameters command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0x10 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A. The argument maybe represented by a result code 0x00 in case of Success, and by a resultcode 0x10 in case of Automatic Parameter Control Failure. When ReadCycle and Read Delay Time have invalid parameters, the argument may berepresented by a result code 0x0E. In case of Not Supported Command, theargument may be represented by 0x17. FIG. 39 illustrates the structureof a response protocol message for the case of Success.

[3.2] Tag Read Category

[3.2.1] Command for Reading a Tag UID (Read Type B UID)

A read type B UID command is used to read a UID of an ISO 18000-B tag.The UID has a length of 64 bits and is essential when a write operationis performed on a corresponding tag. A 40-bit SUID may be used insteadof the 64-bit UID. However, the present invention is described withrespect to the use of the 64-bit UID. The read type B UID command isused to read 8th through 16th address values from a tag, whichcorrespond to the length of UII Set and the length of AD Set,respectively. The address values are, respectively;

08˜09: Tag manufacturer

10˜11: Hardware Type

12: Embedded Application code

13: Application Family ID

14: Storage Data Format (Referring to ISO/IEC 15961 8.2, 15962 B.63, and15962 E.4)

15: Length of UII Set (bytes)

16: Length of AD Set (bytes)

The read type B UID command includes a message type and a code, but doesnot include a payload type and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0x21 indicating Read Type B UID. FIG. 40 illustrates the structure of aprotocol message for the read Type B UID command.

A response to the read type B UID command includes a message type, acode, a payload type, and an argument. The message type may berepresented by 0x01 indicating a response. The code may be representedby 0x21 in case of Success, and by 0xFF in case of Failure. The payloadtype may be represented by Payload Type M in case of Success, andPayload Type A in case of Failure or when there is no tag to be read (NoTag Detected).

The argument represent Success, No Tag Detected, and Failure. In case ofSuccess, the argument may be represented by the UID, Manufacturer,Hardware Type, Embedded Application Code (EAC), Application Family ID(AFID), Storage Data Format (SDF), UII Set Length, and the AD SetLength. In case of No Tag Detected, the argument may be represented by aresult code 0x15. In case of Read Failure, the argument may berepresented by a result code 0x09. In case of Not Supported Command, theargument may be represented by a result code 0x17. FIG. 41 illustratesthe structure of a response protocol message for the read type B UIDcommand for the case where UID=0xE035000000000001, Manufacturer=0x1234,Hardware Type=0x5678, EAC=0x0A, AFID=0x01, SDF=0x00, UII Set Length=8,and AD Set Length=16.

[3.2.2] Command for Reading a UID Block of a Tag (Read Type C UII Block)

A read type C UII block command is used to read and inform a UII blockof an ISO 18000-C tag. The UII block exists in a UII memory bank of atag and denotes all of UII or UII Set and a PC section of the type Ctag. The UII or the UII Set has a variable length, while the PC sectionhas a fixed length. Therefore, when interpreting a response, the lengthof the UII or the UII Set can be found by subtracting 2 from PayloadLength.

The read type C UII block command includes a message type and a code,but does not include a payload type and an argument. The message typemay be represented by 0x00 indicating a command. The code may berepresented by 0x22 indicating Read Type C UII Block. FIG. 42illustrates the structure of a protocol message for the read Type C UIIBlock command.

A response to the read type C UII Block command includes a message type,a code, a payload type, and an argument. The message type may berepresented by 0x01 indicating a response. The code may be representedby 0x22 in case of Success, and by 0xFF in case of Failure. The payloadtype may be represented by Payload Type H in case of Success, andPayload Type A in case of Failure or in case of No Tag Detected.

In case of Success, the argument may be represented by the UII Block(UII+PC). In case of No Tag Detected, the argument may be represented bya result code 0x15. In case of Read Failure, the argument may berepresented by a result code 0x09. FIG. 43 illustrates the structure ofa Read Type C UII Block Response protocol message for the case of a96-bit UII, that is, the case where PC=0x2000, andUII=0x30F4257BF4625F8000000002.

[3.2.3] Command for Reading a User Memory Bank Area of a Tag (Read TypeB User Data)

A read type B user data command is used to read a user memory bank areaof an ISO 18000-B tag. The user memory bank area is read by its lengthfrom a start address. In Type B, since UII or UII Set is stored in thefirst address of the user memory bank area, the start address must beset to ‘0’ to read the UII or the UII Set.

The read type B user data command includes a message type, a code, apayload type, and an argument. The message type may be represented by0x00 indicating a command. The code may be represented by 0x23indicating Read Type B User Data. The payload type may be represented byPayload Type I. The argument may include a 64-bit UID of a tag to read auser memory bank, a 16-bit start address of a user memory bank area, and16-bit length (User Data Length, on a byte basis) by which the usermemory bank area is to be read. FIG. 44 illustrates the structure of aprotocol message for the read type B user data command for the casewhere UID=0xE035000000000001, Start Address=0x0000, and Length=8 byte.

A response to the read type B user data command includes a message type,a code, a payload type, and an argument. The message type may berepresented by 0x01 indicating a response. The code may be representedby 0x23 in case of Success, and by 0xFF in case of Failure. The payloadtype may be represented by Payload Type B in case of Success, and byPayload Type A in case of Failure or in case of No Tag Detected. In caseof Success, the argument may include the contents of the user memorybank (e.g., UII Set). In case of No Tag Detected, the argument mayinclude a result code 0x15. In case of Read Failure, the argument mayinclude a result code 0x09. In case of No User Data, the argument mayinclude a result code 0x1C. In case of Not Supported Command, theargument may include a result code 0x17. FIG. 45 illustrates thestructure of a response protocol message to the Read Type B user datacommand for the case where UII Set=0x123456789ABCDEF0.

[3.2.4] Command for Reading a User Memory Bank Area of a Tag (Read TypeC User Data)

A read type C user data command is used to read a user memory bank areaof an ISO 18000-C tag. The user memory bank area is read by its lengthfrom a start address. When a protocol message for the read type C userdata command is written, UII or UII Set indicating a tag to read theuser memory bank is needed. The UII or the UII Set has a variablelength, while other arguments have a fixed length. Therefore, PayloadLength can be found by adding 4 to the length of the UII or the UII Set.

The read type C user data command includes a message type, a code, apayload type, and an argument. The message type may be represented by0x00 indicating a command. The code may be represented by 0x24indicating Read Type C User Data. The payload type may be represented byPayload Type J. The argument may include a 64-bit UID or UII Set(variable length) of a tag to read a user memory bank, a 16-bit startaddress of a user memory bank area, and 16-bit length (User Data Length,on a byte basis) by which the user memory bank area is to be read. FIG.46 illustrates the structure of a protocol message for the read type Cuser data command for the case where UID=0x30F4257BF8000000002, StartAddress=0x0000, and Length=15 byte.

A response to the read type C user data command includes a message type,a code, a payload type, and an argument. The message type may berepresented by 0x01 indicating a response. The code may be representedby 0x24 in case of Success, and by 0xFF in case of Failure. The payloadtype may be represented by Payload Type G in case of Success, and byPayload Type A in case of Failure, No Tag Detected, or No User Data.

In case of Success, the argument may include the contents of the usermemory bank. In case of No Tag Detected, the argument may include aresult code 0x15. In case of Read Failure, the argument may include aresult code 0x09. In case of No User Data, the argument may include aresult code 0x1C. FIG. 47 illustrates the structure of a responseprotocol message to the Read Type C user data command for the case wherethe contents of the user memory bank=‘FLATRON L1740BQ’.

[3.2.5] Command for Reading the Entire Contents of a Tag (Read EntireType B Tag)

A Read Entire Type B Tag command is used to read the entire contents ofan ISO 18000-B tag, and the entire contents of the tag is received as aresponse. However, a user memory bank is read by a predetermined length.Since only data read from a user memory bank area of all fields of theresponse have a variable length, this length can be found by subtracting24 from Payload Length. Wherein, a memory layout is represented by 12ththrough 17th address of Type B Tag. The value of 12th through 17thaddress is referred to the value of address of the Read Type B UIDcommand.

The Read Entire Type B Tag command includes a message type, a code, apayload type, and an argument. The message type may be represented by0x00 indicating a command. The code may be represented by 0x25indicating Read Entire Type B Tag. The payload type may be representedby Payload Type K. The argument may include a 16-bit User Data Lengthindicating the size of data read from the user memory bank. FIG. 48illustrates the structure of a protocol message for the Read Entire TypeB Tag command for the case where User Data Length=15.

A response message for the Read Entire Type B Tag command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0x25 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type L in case ofSuccess, and by Payload Type A in case of Failure or No Tag Detected.

In case of Success, the argument may include UID, Manufacturer, HardwareType, Memory Layout, and User Data. In case of No Tag Detected, theargument may include a result code 0x15. In case of Read Failure, theargument may include a result code 0x09. In case of Not SupportedCommand, the argument may include a result code 0x17. FIG. 49illustrates the structure of a response protocol message to the ReadEntire Type B Tag command for the case where UID=0xE035000000000001,Manufacturer=0x1234, H/W Type=0x5678, Memory Layout=0x000000000000, andData to be written=‘FLATRON L1740BQ.

[3.2.6] Command for Reading the Entire Contents of a Tag (Read EntireType C Tag)

A Read Entire Type C Tag command is used to read the entire contents ofan ISO 18000-C tag. The ISO 18000-C tag has four memory banks includingReserved, TID, UII, and User Data. This command is used to read threememory banks including TID, UII, and User Data, except Reserved.

The Read Entire Type C Tag command includes a message type, a code, apayload type, and an argument. The message type may be represented by0x00 indicating a command. The code may be represented by 0x26indicating Read Entire Type C Tag. The payload type may be representedby Payload Type K. The argument may include a 16-bit User Data Lengthindicating the size of data read from the user memory bank. FIG. 50illustrates the structure of a protocol message for the Read Entire TypeC Tag command for the case where User Data Length=14.

A response message for the Read Entire Type C Tag command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0x26 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type N in case ofSuccess, and by Payload Type A in case of Failure or No Tag Detected.

In case of Success, the argument may include a TID memory bank, UII orUII Set, PC, and data read from the user memory bank. In case of No TagDetected, the argument may include a result code 0x15. In case of ReadFailure, the argument may include a result code 0x09. FIG. 51illustrates the structure of a response protocol message to the ReadEntire Type C Tag command for the case where TID=0xA98654E2, PC=0x2000,96-bit UII=0x30F4257BF4625F8000000002, and Data of User MemoryBank=‘FLATRON L1740B.

[3.2.7] Command for Starting an Automatic Tag Read Operation (StartAutomatic Read)

A Start Automatic Read command is used to start an automatic tag readoperation. A protocol message constituting this command may include amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x00 indicating a command. The code may berepresented by 0x27 indicating Start Automatic Read. The payload typemay be represented by Payload Type 0.

The argument may be represented by an 8-bit Command Code (0x21˜0x26; anautomatic read operation is not performed for other values) and a 16-bitRepeat Cycle. The 8-bit Command Code indicates a code of a command toperform an automatic read operation. When a read operation of adesignated unit in a Read Cycle is regarded as one Repeat Cycle, the16-bit Repeat Cycle indicates the number of times of repetition of theRepeat Cycle (i.e., the reading number of times=ReadCycle×RepeatCycle).FIG. 52 illustrates the structure of a protocol message for the StartAutomatic Read command for the case where Read Entire Type C Tag, AccessPassword=0x12345678, and Read Cycle=100.

A response protocol message for the Start Automatic Read commandincludes a message type, a code, a payload type, and an argument. Themessage type may be represented by 0x01 indicating a response. The codemay be represented by 0x27 in case of Success, and by 0xFF in case ofFailure. The payload type may be represented by Payload Type A.

In case of Success, the argument may include a result code 0x00. In caseof Automatic Read Failure, the argument may include a result code 0x0A,a result code 0x0E for the case where a code of the command is not inthe range of 0x21˜0x26, a result code 0x0E for the case where RepeatCycle is not ‘0’, and a result code 0x0B for the case where an automaticread operation is being performed (Automatic Read in Operation). FIG. 53illustrates the structure of a response protocol message for the case ofSuccess.

A notification message may be used for Start Automatic Read. Thisnotification message may include a message type, a code, a payload type,and an argument. The message type may be represented by 0x02 indicatingNotification. The code may be identical to the command code that is usedas the argument in the Start Automatic Read command. In case where dataread from a tag is transmitted, the payload type may be identical to theresponse corresponding to a command code 0x21˜0x26. In case where theautomatic read operation is performed by the predetermined number oftimes and thus completed (Automatic Read Completed), the payload typemay be represented by Payload Type A.

Meanwhile, in case where data read from a tag is transmitted, theargument may be identical to a response corresponding to a command code0x21˜0x26. In case where the automatic read operation is performed bythe predetermined number of times and thus completed (Automatic ReadCompleted), the argument may include a result code 0x1F. When there areno more tags to read (No more Tags to Read), the argument may include aresult code 0x20. FIG. 54 illustrates the structure of a notificationprotocol message for the case of Automatic Read Completed. In case wheredata read from a tag is transmitted, the notification protocol messagemay be identical to the response corresponding to the command code0x21˜0x26.

[3.2.8] Command for Stopping an Automatic Tag Read Operation (StopAutomatic Read)

A Stop Automatic Read command is used to stop an automatic tag readoperation. The Stop Automatic Read command includes a message type and acode, but does not include a payload type, and an argument. The messagetype may be represented by 0x00 indicating a command. The code may berepresented by 0x28 indicating Stop Automatic Read. FIG. 55 illustratesthe structure of a protocol message for the Stop Automatic Read commandfor the case of Read Entire Type A Tag command.

A response protocol message for the Stop Automatic Read command includesa message type, a code, a payload type, and an argument. The messagetype may be represented by 0x01 indicating a response. The code may berepresented by 0x28 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A. In case ofSuccess, the argument may include a result code 0x00. In case of CannotStop Automatic Read, the argument may include a result code 0x0C. Incase where an automatic read operation is not being performed, theargument may include a result code 0x0D. FIG. 56 illustrates thestructure of a protocol message for the Stop Automatic Read Response forthe case of Success.

[3.3] Tag Write Category

[3.3.1] Command for Writing a UII Block in a UII Memory Bank of a Tag(Write Type C UII Block)

A Write Type C UII Block command is used to write a UII block in a UIImemory bank of an ISO 1800-C tag, wherein CRC is calculated and processby the mobile RFID reader. The Write Type C UII Block command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x00 indicating a command. The code may berepresented by 0x41 indicating Write Type C UII Block. The payload typemay be represented by Payload Type P. The argument may include a 32-bitAccess Password for writing a Type C tag, a 16-bit UII Length forrepresenting the length of UII or UII Set, a UII or UII Set (variable)for indicating a tag to be written in, a 16-bit New UII Length forrepresenting the length of new UII or UII Set, a New UII or UII Set(variable) for representing a New UII or UII Set to be written in thetag, and a PC for representing a PC value to be written in the tag. FIG.57 illustrates the structure of a protocol message for the Write Type CUII Block command for the case where Access Password=0x87651234,UII=0x30F4257BF46258000000001, New UII=0x30F4257BF46258000000002, andPC=0x2000.

A response message for the Write Type C UII Block command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0x41 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A. The argument mayinclude a result code 0x00 for the case of Success, a result code 0x10for the case of Write Failure, and a result code 0x17 for the case ofNot Supported Command. FIG. 58 illustrates the structure of a responseprotocol message for the Write Type C UII Block command.

[3.3.2] Command for Writing the Entire Contents of a Tag (Write Type BUser Data)

A Write Type B User Data command is used to write the entire contents ofan ISO 1800-B tag. The Write Type B User Data command includes a messagetype, a code, a payload type, and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0x42 indicating Write Type B User Data. The payload type may berepresented by Payload Type Q. The argument may include a 64-bit UID ofa tag to be written in, a 16-bit Start Address representing a startaddress of a user memory bank area in which data are to be written, a16-bit Length representing the size (on a byte basis) of data to bewritten, and a User Data (variable) to be written in the user memorybank by a length designated by the 16-bit Length. FIG. 59 illustratesthe structure of a protocol message for the Write Type B User Datacommand for the case where UID=0xE35000000000001, Start Address=0x00,Length=15, and User Memory Bank=‘FLATRON L1740BQ.

A response message for the Write Type B User Data command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0x42 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A. The argument mayinclude a result code 0x00 for the case of Success, a result code 0x15for the case of No Tag Detected, a result code 0x10 for the case ofWrite Failure, and a result code 0x17 for the case of Not SupportedCommand. FIG. 60 illustrates the structure of a response protocolmessage for the Write Type B User Data command.

[3.3.3] Command for Writing the Entire Contents of a Tag (Write Type CUser Data)

A Write Type C User Data command is used to write the entire contents ofan ISO 1800-C tag. The Write Type C User Data command includes a messagetype, a code, a payload type, and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0x43 indicating Write Type C User Data. The payload type may berepresented by Payload Type R. The argument may include a 32-bit AccessPassword necessary for writing data in a user memory bank area, a 16-bitUII Length (variable) representing the length of UII or UII Set, a16-bit Start Address representing a start address of the user memorybank area in which data are to be written, a 16-bit User Data Lengthrepresenting the size (on a byte basis) of data to be written, and aUser Data (variable) to be written corresponding to a length designatedby the 16-bit User Data Length. FIG. 61 illustrates the structure of aprotocol message for the Write Type C User Data command for the casewhere Access Password=0x87651234, UII=0x30F4257BF46258000000001, StartAddress=0x00, and Data to be written=‘FLATRON L1740BQ’.

A response message for the Write Type C User Data command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0x43 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A. The argument mayinclude a result code 0x00 for the case of Success, a result code 0x15for the case of No Tag Detected, a result code 0x10 for the case ofWrite Failure, and a result code 0x17 for the case of Not SupportedCommand. FIG. 62 illustrates the structure of a response protocolmessage for the Write Type C User Data command.

[3.3.4] Command for Writing the Entire Contents in a Tag (Write EntireType B Tag)

A Write Entire Type B Tag command is used to write the entire contentsin an ISO 1800-B tag. Data can be written in UID, Memory Layout and auser memory bank area. However, regions of Manufacture and H/W Type aredesignated at a manufacturing stage and thus cannot be written.

The Write Entire Type B Tag command includes a message type, a code, apayload type, and an argument. The message type may be represented by0x00 indicating a command. The code may be represented by 0x44indicating Write Entire Type B Tag. The payload type may be representedby Payload Type S. The argument may include a 64-bit UID of a Type B tagto be written, a 48-bit Memory Layout that can be designated and writtenby User Application (if necessary), a 16-bit User Data Length indicatingthe size of data to be written in the user memory bank, and a User Dataindicating data to be written in the user memory bank of a tag (ifnecessary). FIG. 63 illustrates the structure of a protocol message forthe Write Entire Type B Tag command for the case whereUID=0xE35000000000001, Memory Layout=0x000000000000, and Data to bewritten=‘FLATRON L1740BQ’.

A response protocol message for the Write Entire Type B Tag commandincludes a message type, a code, a payload type, and an argument. Themessage type may be represented by 0x01 indicating a response. The codemay be represented by 0x44 in case of Success, and by 0xFF in case ofFailure. The payload type may be represented by Payload Type A. Theargument may include a result code 0x00 for the case of Success, aresult code 0x15 for the case of No Tag Detected, a result code 0x10 forthe case of Write Failure, and a result code 0x17 for the case of NotSupported Command. FIG. 64 illustrates the structure of a responseprotocol message for the Write Entire Type B Tag command.

[3.3.5] Command for Writing the Entire Contents in a Tag (Write EntireType C Tag)

A Write Entire Type C Tag command is used to write the entire contentsin an ISO 1800-C tag. The Write Entire Type C Tag command is useful forsimultaneously writing a MI Block and a user memory bank. Also, theWrite Entire Type C Tag command can be used to write a Reserved Bankarea in which Kill Password and Access Password are sequentiallyincluded. If a password needs to be changed, it must be written in aReserved Bank area.

The Write Entire Type C Tag command includes a message type, a code, apayload type, and an argument. The message type may be represented by0x00 indicating a command. The code may be represented by 0x45indicating Write Entire Type C Tag. The payload type may be representedby Payload Type T.

The argument may include a 32-bit Access Password for writing a Type Ctag, a 16-bit UII Length for representing the length of UII or UII Set,a UII or UII Set (variable) for indicating a tag to be written in, a16-bit New UII Length for representing the length of new UII or UII Set,a New UII or UII Set (variable) for representing a New UII or UII Set tobe written in the tag, a 64-bit PC to be written in the tag, a User Dataused when there are data to be written in a user memory bank of the tag,a 16-bit Reserved Bank Length representing the length of data to bewritten in a reserved bank, a Reserved Bank Data (variable) to bewritten in the reserved bank.

FIG. 65 illustrates the structure of a protocol message for the WriteEntire Type C Tag command for the case where Access Password=0x87651234,UII=0x30F4357BF46258000000001, New UII=0x30F4357BF46258000000002,PC=0x2000, Data to be written='FLATRON L1740BQ’, KillPassword=0x12345678, and Access Password=0x87654321.

A response protocol message for the Write Entire Type C Tag commandincludes a message type, a code, a payload type, and an argument. Themessage type may be represented by 0x01 indicating a response. The codemay be represented by 0x45 in case of Success, and by 0xFF in case ofFailure. The payload type may be represented by Payload Type A.

The argument may include a result code 0x00 for the case of Success, aresult code 0x15 for the case of No Tag Detected, a result code 0x10 forthe case of Write Failure, and a result code 0x17 for the case of NotSupported Command. FIG. 66 illustrates the structure of a responseprotocol message for the Write Entire Type C Tag command for the case ofSuccess.

[3.4] Tag Kill Category

[3.4.1] Command for Killing a Tag (Kill Type C Tag)

A Kill Type C Tag command is used to kill an ISO 1800-C tag. AccessPassword and Kill Password are all required for the killing operation,which aims at security.

The Kill Type C Tag command includes a message type, a code, a payloadtype, and an argument. The message type may be represented by 0x00indicating a command. The code may be represented by 0x61 indicatingKill Type C Tag. The payload type may be represented by Payload Type U.

The argument may include a 32-bit Access Password required for accessinga tag, a 32-bit Kill Password required for killing a tag, a 16-bit UIILength indicating the length of UII or UII Set, and a UII or UII Set(variable) indicating a Type C tag to be killed. FIG. 67 illustrates thestructure of a protocol message for the Kill Type C Tag command for thecase where Access Password=0x12345678, Kill Password=0x87654321, andUII=0x30F4357BF46258000000001.

A response message for the Kill Type C Tag command includes a messagetype, a code, a payload type, and an argument. The message type may berepresented by 0x01 indicating a response. The code may be representedby 0x61 in case of Success, and by 0xFF in case of Failure. The payloadtype may be represented by Payload Type A.

The argument protocol may include a result code 0x00 for the case ofSuccess, a result code 0x15 for the case where there is no tag to bekilled (No Tag Detected), and a result code 0x12 for the case of KillFailure. FIG. 68 illustrates the structure of a response protocolmessage for the Kill Type C Tag command for the case of Success.

[3.5] Tag Lock Control Related Category

[3.5.1] Command for Controlling Lock of a Type B Tag (Lock Type B Tag)

A Lock Type B Tag command is used to control lock of a Type B tag. TheLock

Type B Tag command includes a message type, a code, a payload type, andan argument. The message type may be represented by 0x00 indicating acommand. The code may be represented by 0x81 indicating Lock Type B Tag.The payload type may be represented by Payload Type V.

The argument may include a 64-bit UID required for selecting a tag to belocked, and an 8-bit Address (0x00˜0xFF) representing an address of atag to be killed. FIG. 69 illustrates the structure of a protocolmessage for the Lock Type B Tag command for the case whereUID=0xE035000000000001 and the 30^(th) block is locked.

A response protocol message for the Lock Type B Tag command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0x81 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A.

The argument may include a result code 0x00 for the case of Success, aresult code 0x15 for the case where there is no tag to be locked (No TagDetected), a result code 0x13 for the case of Lock Control Failure, anda result code 0x17 for the case of Not Supported Command. FIG. 70illustrates the structure of a response protocol message for the LockType B Tag command for the case of Success.

[3.5.2] Command for Controlling Lock of a Type C Tag (Lock Type C Tag)

A Lock Type C Tag command is used to control lock of a Type C tag. TheLock

Type C Tag command includes a message type, a code, a payload type, andan argument. The message type may be represented by 0x00 indicating acommand. The code may be represented by 0x82 indicating Lock Type C Tag.The payload type may be represented by Payload Type W. The argument mayinclude a 32-bit Access Password required for a locking operation, a16-bit UII Length indicating the length of UII or UII Set, a UII or UIISet (variable) indicating a Type C tag to be locked, and a 24-bit LockData for controlling a locking operation (use a 20-bit flag forcontrolling a locking operation and the less significant 20 bits; theless significant 4 bits=‘0’). FIG. 71 illustrates the structure of aprotocol message for the Lock Type C Tag command for the case whereUII=0x30F4257BF46258000000001, Access Password=0x87654321, and a UIIcode is permanently locked.

A response protocol message for the Lock Type C Tag command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0x82 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A.

The argument may include a result code 0x00 for the case of Success, aresult code 0x15 for the case where there is no tag to be locked (No TagDetected), a result code 0x13 for the case of Lock Control Failure, anda result code 0x17 for the case of Not Supported Command. FIG. 72illustrates the structure of a response protocol message for the LockType C Tag command for the case of Success.

[3.6] Additional Function Category

[3.6.1] Command for Getting the Last Result Code (Get Last Result)

A Get Last Result command is used to get the last result code. The GetLast Result command includes a message type and a code, but does notinclude a payload type and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0xA1 indicating Get Last Result. FIG. 73 illustrates the structure of aprotocol message for the Get Last Result command.

A response protocol message for the Get Last Result command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0xA1 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A. The argument mayinclude the last result code for the case of Success, a result code 0x14for the case of Cannot Get Last Result, and a result code 0x17 for thecase of Not Supported Command. FIG. 74 illustrates the structure of aresponse protocol message for the case where the last result is ReadFailure.

[3.6.2] Command for Starting a Test Mode (Start Test Mode)

A Start Test Mode command is used to change the RFID reader into a testmode. The Start Test Mode command includes a message type and a code,but does not include a payload type and an argument. The message typemay be represented by 0x00 indicating a command. The code may berepresented by 0xA2 indicating Start Test Mode. FIG. 75 illustrates thestructure of a protocol message for the Start Test Mode command.

A response protocol message for the Start Test Mode command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0xA2 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A. The argument mayinclude a result code 0x00 for the case of Success, and a result code0x1E for the case of Test Mode Control Failure. FIG. 76 illustrates thestructure of a response protocol message for the case of Success.

[3.6.3] Command for Stopping a Test Mode (Stop Test Mode)

A Stop Test Mode command is used to stop a test mode of the reader. TheStop Test Mode command includes a message type and a code, but does notinclude a payload type and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0xA3 indicating Stop Test Mode. FIG. 77 illustrates the structure of aprotocol message for the Stop Test Mode command.

A response protocol message for the Stop Test Mode command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0xA3 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A.

The argument may include a result code 0x00 for the case of Success, anda result code 0x1E for the case of Test Mode Control Failure. FIG. 78illustrates the structure of a response protocol message for the StopTest Mode command for the case of Success.

[3.6.4] Command for Starting a Receive Test Mode (Start Receive Test)

A Start Receive Test command can be used only in a test mode, and isused to test the receive sensitivity of the reader. Upon receiving theStart Receive Test command, the reader enters a receive standby mode toaccumulatively add the number of successfully-received bits.

The Start Receive Test command includes a message type and a code, butdoes not include a payload type and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0xA4 indicating Start Test Mode. FIG. 79 illustrates the structure of aprotocol message for the Start Receive Test command.

A response protocol message for the Start Receive Test command includesa message type, a code, a payload type, and an argument. The messagetype may be represented by 0x01 indicating a response. The code may berepresented by 0xA4 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type A.

The argument may include a result code 0x00 for the case of Success, anda result code 0x1D for the case where the reader is not in a test mode.FIG. 80 illustrates the structure of a response protocol message for theStart Receive Test command for the case of Success.

[3.6.5] Command for Stopping a Receive Test (Stop Receive Test)

A Stop Receive Test command can be used only in a test mode, and is usedto test the receive sensitivity of the reader. When receiving the StopReceive Test command, the reader exits the standby mode to receive anA/I packet and then transmits the number of successfully-received bitsto the processor.

The Stop Receive Test command includes a message type and a code, butdoes not include a payload type and an argument. The message type may berepresented by 0x00 indicating a command. The code may be represented by0xA5 indicating Stop Test Mode. FIG. 81 illustrates the structure of aprotocol message for the Stop Receive Test command.

A response protocol message for the Stop Receive Test command includes amessage type, a code, a payload type, and an argument. The message typemay be represented by 0x01 indicating a response. The code may berepresented by 0xA5 in case of Success, and by 0xFF in case of Failure.The payload type may be represented by Payload Type G in case ofSuccess, and by Payload Type A in case of Failure. In case of Success,the argument may include a 32-bit value indicating the number ofreceived bits. In case of Test Mode Control Failure, the argument mayinclude a result code 0x1E. FIG. 82 illustrates the structure of aresponse protocol message for the case where the number of received bitsis 100000.

[3.7] Appendices for Command, Response, and Notification

[3.7.1] Commonly Applied Result Codes

The following result codes are commonly used for all of commands,responses and notifications.

-   -   Success: The result generated when a command is successfully        executed, which can be represented by, for example, 0x00.    -   Invalid Parameter: The result generated when an argument of a        command has an invalid value, which can be represented by, for        example, 0x0E.    -   Not Supported Command: The result generated when the reader        cannot support a command. An optional command may not be        implemented in the reader. The result can be used in this case.        This code can be represented by, for example, 0x17.

Undefined Command: The result generated when the reader receives acommand that was not defined by the present invention or the vendor,which can be represented by, for example, 0x18.

-   -   Reader is not in Test Mode: The result generated when a command        usable only in a test mode is issued when the reader is not in        the test mode, which can be represented by, for example, 0x1D.

[3.7.2] Valid Value Ranges of Parameters Used in Commands

Table 12 below illustrates valid value ranges of parameters used in eachcommand. When a parameter value deviates from such range, theaforementioned Invalid Parameter (0x0E) error code must be included in aresponse message to be transmitted. Since Table 12 does not deal withparameters for a password necessary for a Type C tag related command, acommand of a tag write category, commands of a tag lock control relatedcategory, such parameters must be based on the corresponding standarddocument.

TABLE 12 Valid Value Command Use Parameter Range Reader Power Control8-bit arg 0x00 or 0xFF Reader Connection Control 8-bit arg 0x00 or 0xFFGet Reader Info 8-bit arg 0x00~0x04 Set Signal Strength 8-bit arg0x00~0x64 Set Region 8-bit arg 0x01~0x1F Set Type B A/I Parameters Basedon ISO 18000-6B Standards Set Type C A/I Select Based on ISO 18000-6CStandards Parameters Set Type C A/I Query Based on ISO 18000-6CStandards related Parameters Set Automatic Read 16-bit Read Cycle0x0001~0xFFFF Parameters 8-bit Read Delay Time 0x00~0xFF Read Type BUser Data 16-bit User Data Length 0x0001~0xFFFF Read Type C User Data16-bit User Data Length 0x0001~0xFFFF Start Automatic Read 16-bit RepeatCycle 0x0001~0xFFFF

[3.7.3] Process Performed when there is No Response to a Command.

In the RFID reader control system according to the present invention,the following process is performed when there is no response to acommand issued from the processor to the reader.

When a driver receives no response from the reader even after apredetermine time from the transmission time of a command, it transmitsan error message to an upper layer. A response message received rightafter the above process is disregarded and deleted. A response waitingtime Trespdly may be set to a predetermined value, for example, 500msec. When a corresponding default value is adjusted, a changed valuemust be clearly expressed.

[3.7.4] Management of Reader Status

For management of a reader status, a reader power status and a readerconnection status are managed by the driver.

[3.7.5] Details about Notification Related to Automatic Read

When two or more tags are read, one notification must be performed foreach of the read tags. When there is no tag to be read by the reader,the reader transmits a result code of ‘No more Tags to Read’ by anotification using a payload type A and stops an automatic readoperation. Such notification must be clearly transmitted to an upperlayer.

[4] Test Certification and Test Mode

The present invention enables test certification to be performed on theA/I protocol standards implemented in a mobile RFID reader according tothe mobile RFID forum test certification standards. For the testcertification, the A/I section defined in the ISO 18000-6C standards ismandatory and the contents about the ISO 18000-6B standards areoptional.

[4.1] Test Mode

In the test mode, a protocol defined in the A/I standards implemented ina mobile RFID reader for test certification is received as it is, and togive a response thereto is supported. That is, a command is directlygiven in the format of a protocol defined in the A/I standards, and aresponse thereto is also received in the format of a protocol defined inthe A/I standards. As above, a protocol message defined in the A/Istandards is used, as it is, to make it possible to perform the testcertification.

In order to convert the reader into the test mode, correspondingcommands within the abovementioned additional category must be used. Atthis time, the reader must be in a power-on state and must be connectedto the processor. The corresponding commands are the Start Test Modecommand and the Stop Test Mode command that have been described above.When the Start Test Mode command is executed, a response thereto isreceived. When a normal response is received, the reader converts intothe test mode. In the test mode, only a protocol message having amessage type field of 0x03 in its header can be used. That is, commandsof several categories defined above cannot be used. When receiving ageneral command in the test mode, the reader transmits the result codeof ‘Reader is not in Test Mode’ to the processor and disregards thegeneral command.

The Stop Test Mode command is use to stop the test mode. When receivingthe Stop Test Mode command, the reader exits the test mode and canreceive and process a general command.

[4.2] Protocol Message in Test Mode

In the test mode, an A/I protocol to receive the test certification canbe used as it is. The A/I protocol is encapsulated into the payloadfield defined in the present invention. The contents of the protocolmessage in the test mode are as follows:

Preamble and End Mark values are used in the same manner.

The Message Type field of a header uses information (e.g., 0x03)indicating a protocol message in the test mode.

The Code field of the header includes a value 0x00 in case of a commandbased on the A/I protocol, and includes a value 0x01 in case of aresponse. A command is a protocol message that is transmitted from areader to a tag, while the response is a protocol message that istransmitted from a tag to a reader.

The Payload Length field of the header indicates the total length of theA/I protocol message included in the payload.

The payload field itself corresponds to the A/I protocol message.

FIG. 83 illustrates the structure of a protocol message used in the testmode.

[4.3] Procedure for Processing Protocol Message in Test Mode

The RFID reader may process a protocol message of the test modeaccording to the following procedure.

[4.3.1] When the Reader Receives a Message in the Test Mode

(a). The reader reads a header field from a message received accordingto an RFID protocol.

(b). The reader checks a preamble.

(c). The reader ascertains that a Message Type field value is 0x03

(d). The reader ascertains that a Code field value is 0x00

(e). The reader reads the Read Payload Length field to check the lengthof an A/I protocol message in a payload section

(f). The reader reads the A/I protocol message from the payload sectiondesignated by the Payload Length field

(g). The reader transfers the read A/I protocol message to the A/I unit.The A/I unit transfers the received A/I protocol message to a tag.

[4.3.2] When the Reader Transmits a Message in the Test Mode

(a). An A/I unit receives an A/I protocol message from a tag.

(b). The received A/I protocol message itself acts as a payload.

(c). The entire A/I protocol message is inserted into a Payload Lengthfield.

(d). A Code field value is set to 0x01.

(e). A Message Type field value is set to 0x03.

(f). Preamble and End Mark are added and transmitted.

[4.4] Test the Receive Sensitivity of the Reader

In the test mode, two commands are provided to test the receivesensitivity of the reader. The two commands are respectively the StartReceive Test command and the Stop Receive Test command that are definedin the additional function category.

When the Start Receive Test command is issued, the reader enters areceive standby mode. In the receive standby mode, a BER can bemeasured. In the receive sensitivity test, an A/I packet, a bit pattern,or a PN code may be used. When receiving them, the reader mustaccumulatively add the number of successfully-received bits.

When the receive sensitivity test ends, the Stop Receive Test command istransmitted and thus the number of the successfully-received bits isreceived by a response. A ratio of the number of thesuccessfully-received bit to the number of bits transmitted in a testenvironment is obtained to calculate the BER.

Meanwhile, the content of an A/I protocol packet for the receivesensitivity test is determined in the test environment. The reader mustsupport to set and change the determined contents.

INDUSTRIAL APPLICABILITY

According to the present invention, it is possible to provide a methodof defining a protocol for controlling an RFID reader and an RFID readercontrol unit (e.g., processor) of a mobile terminal, and constructingand transmitting messages, information, commands, and responses betweenthe RFID reader and the RFID reader control unit.

1-9. (canceled)
 10. A method for getting a parameter, the methodperformed by a mobile processor and comprising: transmitting, to areading device, a getting command, the getting command being for gettinga plurality of parameters, the plurality of parameters used forselecting at least one of a corresponding tag device; receiving, fromthe reading device, a response message in response to the gettingcommand, the response message including the plurality of the parameters,wherein the plurality of the parameters include at least a sectionindicating field, a start address field, a length field, and acomparison value, and wherein the section indicating field specifies anspecific memory area of the tag device, the start address fieldspecifies a start point of the specific memory area of the tag device,the length field specifies a length from the star point, the comparisonvalue includes a bit to be compared with a target value stored in thetag device, the target value extracted from the specific memory areausing the start address field and the length field; and storing thereceived plurality of the parameters.
 11. The method of claim 10,wherein the getting command includes a code discerning a type of acommand.
 12. The method of claim 11, wherein the response messageincludes the code included in the getting command.
 13. The method ofclaim 12, wherein the getting command and the response message operatein pairs.
 14. The method of claim 11, wherein the reading device storesa result code indicating a reason of failure when the getting command isfailed.
 15. A mobile terminal for getting a parameter, comprising: aninterface unit configured to transmit/receive data to/from a readingdevice; a processor configured to: transmit, to the reading device viathe interface unit, a getting command, the getting command being forgetting a plurality of parameters, the plurality of parameters used forselecting at least one of a corresponding tag device, receive, from thereading device via the interface unit, a response message in response tothe getting command, the response message including the plurality of theparameters, wherein the plurality of the parameters include at least asection indicating field, a start address field, a length field, and acomparison value, and wherein the section indicating field specifies anspecific memory area of the tag device, the start address fieldspecifies a start point of the specific memory area of the tag device,the length field specifies a length from the star point, the comparisonvalue includes a bit to be compared with a target value stored in thetag device, the target value extracted from the specific memory areausing the start address field and the length field, and store thereceived plurality of the parameters.
 16. The mobile terminal of claim15, wherein the getting command includes a code discerning a type of acommand.
 17. The mobile terminal of claim 16, wherein the responsemessage includes the code included in the getting command.
 18. Themobile terminal of claim 17, wherein the getting command and theresponse message operate in pairs.
 19. The mobile terminal of claim 16,wherein the reading device stores a result code indicating a reason offailure when the getting command is failed.